@aarongoin ah that's good to know that it's typically included with java IDEs. Yeah, I added for local builds with vscode, attempting to make the experience smoother. I'll rip it out.

@aarongoin oh wait, I just moved lombok out of each module where it was previously and added to the parent pom so the modules could just inherit it. So we only have one spot to maintain it. Are you saying it shouldn't be included in any modules?

@eneumann Well that was my understanding. lombok is a dev dependency--it shouldn't need to be bundled with the java lib at all. I think historically it wasn't needed or included in the POMs because many Java native IDE's provide a way to use it from within the IDE and so I think that's why Gaston never added it to the POM files. But in my latest reading it appears that the <scope>provided</scope> part means Maven considers it a compiler dependency only and shouldn't include it when jarring? So I guess in theory it actually shouldn't hurt anything adding it to the POM like this... In theory! 😜 I suppose we should verify that it's not being included somehow in the final jars just to sanity check... Anyway if we do add it, I like that you've put it in a single place rather than many.